CVE-2022-49816
Xen Memory Leak in Device Add
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
INFO
Published Date :
May 1, 2025, 3:16 p.m.
Last Modified :
May 2, 2025, 6:15 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
- Consult CVE Numbering Authority for details.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-49816 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-49816 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 02, 2025
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 02, 2025
Action Type Old Value New Value Changed Description In the Linux kernel, the following vulnerability has been resolved: xen/pcpu: fix possible memory leak in register_pcpu() In device_add(), dev_set_name() is called to allocate name, if it returns error, the name need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(). Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Removed Reference kernel.org: https://git.kernel.org/stable/c/0199bf0a8f74509736744c9e36f4473a5892a09d Removed Reference kernel.org: https://git.kernel.org/stable/c/6209a85079a035b5c2279b15b197531156b549fa Removed Reference kernel.org: https://git.kernel.org/stable/c/7ed540bcee2e24479524b9705cc7462b2652f944 Removed Reference kernel.org: https://git.kernel.org/stable/c/bb9924a6edd9d4a9ef83a5f337af60f8a7a68f98 Removed Reference kernel.org: https://git.kernel.org/stable/c/c08c13cb13fa3866dd0700db3b246fcd2043ab81 Removed Reference kernel.org: https://git.kernel.org/stable/c/ccb22c876e8e7f62377e749c971907efe65d34c2 Removed Reference kernel.org: https://git.kernel.org/stable/c/da36a2a76b01b210ffaa55cdc2c99bc8783697c5 Removed Reference kernel.org: https://git.kernel.org/stable/c/e948f3c129d78537ded70bcc99c31f0b45f05dd7 -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 01, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: xen/pcpu: fix possible memory leak in register_pcpu() In device_add(), dev_set_name() is called to allocate name, if it returns error, the name need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(). Added Reference https://git.kernel.org/stable/c/0199bf0a8f74509736744c9e36f4473a5892a09d Added Reference https://git.kernel.org/stable/c/6209a85079a035b5c2279b15b197531156b549fa Added Reference https://git.kernel.org/stable/c/7ed540bcee2e24479524b9705cc7462b2652f944 Added Reference https://git.kernel.org/stable/c/bb9924a6edd9d4a9ef83a5f337af60f8a7a68f98 Added Reference https://git.kernel.org/stable/c/c08c13cb13fa3866dd0700db3b246fcd2043ab81 Added Reference https://git.kernel.org/stable/c/ccb22c876e8e7f62377e749c971907efe65d34c2 Added Reference https://git.kernel.org/stable/c/da36a2a76b01b210ffaa55cdc2c99bc8783697c5 Added Reference https://git.kernel.org/stable/c/e948f3c129d78537ded70bcc99c31f0b45f05dd7